[6.x] Chips 🍟 #14766
Merged
Merged
Conversation
Contributor
|
Man, how are we going to translate that option? :-) |
Contributor
Author
|
"Chips" is just what Google calls them in their Material Design guidelines https://m3.material.io/components/chips/ – think like a "poker chip", but they're called "Badges" or "Pills" or "Tokens" elsewhere, if that helps? |
…type Keeps the generic button_group fieldtype clean by moving the radio/checkbox appearance preview UI into its own control_appearance fieldtype. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
A `default` appearance value no longer masks a legacy `inline: true` field. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Adds a migrateConfig hook on fieldtypes so editing/saving a radio or checkboxes field resolves the legacy inline key to appearance and drops it. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of the Problem
Radio buttons and checkboxes are good defaults, but sometimes a different UI presentation can help users.
"Chips" have become popular in UI patterns. Here's an article https://readmedium.com/why-chips-should-replace-checkboxes-and-radio-buttons-52f909a5b8f3.
Chips could be useful when you want larger touch targets, a horizontal layout, or maybe just some variation in your blueprint.
We already have "Appearance" options for certain fields:
What this PR Does
New Options
Radios
Checkboxes
Chips on the Publish Forms
And here's what they look like on a publish form
How to Reproduce